home *** CD-ROM | disk | FTP | other *** search
- You should never need UMSDOCTOR!
-
-
- If your machine has crashed or powered down during a cleanup
- operation, there should be a proper backup of you complete
- message-base somewhere.
-
- If your MB is corrupted after a crash or reset during normal operation
- and cannot be repaired by umsserver itself, you probably didn't use a
- proper 2.0 (or better) filesystem.
-
- In any other case you either have some _very_ weird hardware, run
- _bad_ programs (with "enforcer-hits"), or you have discovered a
- serious bug in umsserver, which the author urgently wants to be
- informed about!
-
-
- However, given you really think there's no other help or the author
- tells you to do so, you can use UMSDOCTOR like that:
-
- 1) make sure the umsserver does NOT run
-
- 1> quitums
-
- 2) 'CD' to the message-base
-
- 1> cd MB:
-
- 3) start UMSDOCTOR and tell it what file it can write to
-
- 1> umsdoctor Spool:umsdoctor.export
-
- Make sure the destination volume ("Spool:" in the expamle) has enough
- free storage (about the same as your MB).
-
- 4) create a new MB and import UMSDOCTOR's output
-
- 1> delete .~(idcount)
- 1> import sysop password Spool:umsdoctor.export restore
-
-
- Known bugs:
- - UMSDOCTOR does not care about links. Crosspostings and
- multi-addresse mails cannot completely be recreated.
-